Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Comment Re:Will it also automatically not blow up extensio (Score 2) 393

Extension compatibility hasn't been a problem since Firefox 10; the max version is now automatically bumped. Furthermore, Firefox 4, 5, and 6 were kind of sucky releases, esp. in terms of memory consumption. Firefox 15 is a much better browser. UI changes since 5 have been minimal. It's also not full of security holes the way older versions now are. You should try it.

Comment Re:Old story, or something new? (Score 1) 393

Try it. Check out the user feedback near the bottom of https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fblog.mozilla.org%2Fnnethercote%2F2012%2F07%2F19%2Ffirefox-15-plugs-the-add-on-leaks%2F -- people have experienced greatly reduced memory consumption, faster painting and scrolling, and fewer pauses.

Comment Re:Problem of perception? (Score 1) 375

The real problem is page faults. People don't notice how much memory a program uses until/unless it starts causing page faults. Some other observations and responses to this thread.
  • One reason that browsers are using more memory over time is that browers are way more capable than they used to be. HTML5, web apps and all that.

  • People say "I have N tabs open, Firefox is using M MB of memory". Often followed by "that seems outrageous" or "that seems reasonable". Without saying what those tabs have in them, it's pretty much useless.

  • Firefox's memory usage has varied over the years. FF2 was terrible, and contributed heavily to the bad reputation. FF3, FF3.5 and FF3.6 were much better. FF4 is worse than FF3.6; FF5 will be better (it already is). Subsequent Firefoxes will hopefully be better again.

Comment Re:All browsers are consuming more memory. (Score 0) 375

Is this per-tab or global?

It's global memory usage at the moment. I'm working on https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fbugzilla.mozilla.org%2Fshow_bug.cgi%3Fid%3D661474 which will give JS memory usage per "compartment", which roughly means "per domain". So if a page at foo.com has a Twitter feed and some Google Analytics stuff, there'll be three compartments, one for foo.com, one for twitter.com, and one for google-analytics.com. It's not quite per-tab, but in that direction. about:memory is evolving, keep an eye on it.

Slashdot Top Deals

Quark! Quark! Beware the quantum duck!

Working...